Systems and methods for point of sale deposits

ABSTRACT

The disclosed embodiments include systems and methods for executing a point of sale deposit. In one embodiment, a system may include one or more memory devices storing software instructions, and one or more processors configured to execute the software instructions to receive transaction information related to a point of sale deposit from a client device, and generate a pending deposit transaction based on the transaction information. The one or more processors may be further configured to execute the software instructions to receive a first transaction token from the client device, receive a second transaction token from a third-party device, match the first transaction token to the second transaction token, and complete the pending deposit transaction based on the match.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.15/899,962, filed Feb. 20, 2018, which is a continuation of U.S. patentapplication Ser. No. 15/797,747, filed Oct. 30, 2017, which is acontinuation of U.S. patent application Ser. No. 14/472,610, filed Aug.29, 2014, which claims priority to U.S. Provisional Application No.61/872,150, filed Aug. 30, 2013 and U.S. Provisional Application No.62/007,612, filed Jun. 4, 2014. The above-referenced applications areexpressly incorporated herein by reference in their entireties.

TECHNICAL FIELD

The disclosed embodiments generally relate to systems and methods forproviding a transaction service, and more particularly, systems andmethods for providing point of sale deposits.

BACKGROUND

Some financial service providers are considered “direct banks.” Directbanks typically offer the same types of financial accounts to consumersas typical banks, but without the same physical presence. For example, acustomer may maintain a checking and savings account with a direct bank;however, the customer will have no physical bank location (e.g., branch)to visit in order to conduct transactions. Customers of direct bankstherefore must rely primarily on online (or telephone) services tomanage their financial accounts.

Customers of direct banks may also rely on merchant services to transactwith their direct bank financial service accounts. For example,merchants often offer customers the ability to make point of sale cashwithdrawals along with their merchant transaction. In this way, acustomer may be able to receive “cash back” after making a debit cardpurchase at a retail store. The customer receives cash from the merchantand an amount equal to the received cash is added to the amounteventually transferred to the merchant from the customer's financialaccount to complete the purchase. Because other options for cashwithdrawals are limited, merchant “cash back” services are especiallyconvenient to customers that have a financial account with a directbank.

Cash deposits, however, remain difficult to complete for customers ofdirect banks using current technology and infrastructure associated withfunds transfers. For example, in order to deposit cash into a financialaccount held with a direct bank, a customer may have to first depositthe cash into another bank and then transfer the funds to the desiredfinancial account. This process can be inconvenient and may take severaldays to complete. There is therefore a need for technology capable ofperforming point of sale deposits.

SUMMARY

Consistent with disclosed embodiments, systems, methods, andcomputer-readable media are provided for point of sale deposits.

Consistent with a disclosed embodiment, a system for executing a pointof sale deposit is provided. The system may include one or more memorydevices storing software instructions. The system may also include oneor more processors configured to execute the software instructions toreceive transaction information related to a point of sale deposit froma client device, and generate a pending deposit transaction based on thetransaction information. The one or more processors may be furtherconfigured to receive a first transaction token from the client device,the first transaction token retaining authorization information, andreceive a second transaction token from a third-party device, the secondtransaction token retaining authorization information. The one or moreprocessor may also be configured to match the first transaction token tothe second transaction token based on the authorization information, andcomplete the pending deposit transaction based on the match.

Consistent with another disclosed embodiment, a system for executing apoint of sale deposit may include one or more I/O devices configured tosend and receive data, one or more memory devices storing softwareinstructions, and one or more processors configured to execute thesoftware instructions to receive transaction information related to apoint of sale deposit at the one or more I/O devices, and identify athird-party based on the received transaction information and transmitthe transaction information to a third-party device via the one or moreI/O devices. The one or more processors may be further configured toreceive a transaction token generated by the third-party device, thetransaction token including the transaction information andauthorization information, transmit the transaction token to a financialservice provider device, and provide the transaction token to a merchantdevice via the one or more I/O devices by generating an opticalrepresentation of the transaction token, and displaying the opticalrepresentation with the one or more I/O devices.

Consistent with yet another disclosed embodiment, a system for executinga point of sale deposit may include one or more memory devices storingsoftware instructions, and one or ore processors configured to executesoftware instructions to receive transaction information related to apoint of sale deposit from a client device, and generate a temporaryfinancial account. The one or more processors may be further configuredto generate a first transaction token associated with the temporaryfinancial account, the first transaction token retaining at least thetransaction information and authorization information, and transmit thefirst transaction token to the client device. The one or more processorsmay also be configured to receive a second transaction token from amerchant device, match the first transaction token to the secondtransaction token, activate the temporary financial account based on thematch; and transmit a third transaction token to a financial serviceprovider device based on the match.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary system, consistent withdisclosed embodiments;

FIG. 2 is a block diagram of an exemplary server, consistent withdisclosed embodiments;

FIG. 3 is a flowchart of an exemplary process for executing a point ofsale deposit, consistent with disclosed embodiments;

FIG. 4 is a flowchart of an exemplary process for initiating a point ofsale deposit, consistent with disclosed embodiments;

FIG. 5 is a flowchart of an exemplary process for executing a point ofsale deposit, consistent with disclosed embodiments;

FIG. 6 is a flowchart of an exemplary process for executing a point ofsale deposit, consistent with disclosed embodiments;

FIG. 7 is a block diagram of an exemplary alternative system, consistentwith disclosed embodiments;

FIG. 8 is a flowchart of an exemplary process for executing a point ofsale deposit with a third-party device, consistent with disclosedembodiments;

FIG. 9 is a flowchart of an exemplary client device point of saledeposit process, consistent with disclosed embodiments;

FIG. 10 is a flowchart of an exemplary third-party device point of saledeposit process, consistent with disclosed embodiments; and

FIG. 11 is a flowchart of an exemplary financial service provider devicepoint of sale deposit process, consistent with disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments,examples of which are illustrated in the accompanying drawings. Whereverconvenient, the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

In one implementation of the disclosed embodiments, a customer may makea deposit into a financial account in combination with anothertransaction with a merchant. For example, a customer may pay cash to amerchant, which may trigger funds being transferred into the customer'sfinancial account. Disclosed embodiments may include hardware devicesthat process these point of sale deposits, thereby providing customerswith a new option for depositing funds, improving efficiency offinancial account management, and reducing the need for physical serviceprovider locations (e.g., bank branches). Further, in some embodiments,point of sale deposits may be processed through a third-party device,which may be a hardware device configured to efficiently facilitate thedeposit.

FIG. 1 is a block diagram illustrating an exemplary system 100 forperforming one or more operations, consistent with the disclosedembodiments. In one embodiment, system 100 may include a client device110, a merchant device 120, a financial service provider device 130, anda network 140. The components and arrangement of the components includedin system 100 may vary. Thus, system 100 may further include one or moreof the components of system 100 or other components that perform orassist in the performance of one or ore processes consistent with thedisclosed embodiments.

Components of system 100 may be computing systems configured to executea point of sale deposit. As further described herein, components ofsystem 100 may include one or more computing devices (e.g., computer(s),server(s), embedded systems, etc.), memory storing data and/or softwareinstructions (e.g., database(s), memory devices, etc.), etc. In someembodiments, the one or more computing devices are configured to executesoftware instructions stored on one or more memory devices to performone or ore operations consistent with the disclosed embodiments.Components of system 100 may be configured to communicate with one ormore other components of system 100, including client device 110,merchant device 120, and financial service provider device 130. Incertain aspects, users may operate one or more components of system 100to initiate one or more operations consistent with the disclosedembodiments. For example, client device 110 may be operated by a user112. User 112 may be an owner/operator of client device 110, such as acustomer. In other aspects, the one or more users may be employees of,or associated with, the entity corresponding to the respectivecomponent(s) (e.g., someone authorized to use the underlying computingsystems or otherwise act on behalf of the entity). For example, merchantdevice 120 may be operated by a user 122. User 122 may be an employee ofa merchant associated with merchant device 120, such as a retail storeemployee. In other aspects, the one or more users may not be an employeeor otherwise associated with the underlying entity. In some aspects, theone or more users may be an entity associated with the respectivecomponent.

Client device 110 may be one or more computing devices that areconfigured to execute software instructions for performing one or moreoperations consistent with the disclosed embodiments. In one example,client device 110 may be a mobile device (e.g., tablet, smartphone,etc.), a desktop computer, a laptop, a server, a wearable screen orheadset, and/or a dedicated hardware device. Client device 110 mayinclude one or more processors configured to execute softwareinstructions stored in memory, such as memory included in client device110. Client device 110 may include software that, when executed by aprocessor, performs known Internet-related communication and contentdisplay processes. For instance, client device 110 may execute browsersoftware that generates and displays interface screens including contenton a display device included in, or connected to, client device 110. Thedisclosed embodiments are not limited to any particular configuration ofclient device 110. For instance, client device 110 may be a mobiledevice that stores and executes mobile applications that providefinancial-service-related functions offered by a financial serviceprovider, such as an application associated with one or more financialaccounts that a customer holds with financial service provider.

In one embodiment, a user 112 may use client device 110 to perform oneor more operations consistent with the disclosed embodiments. In oneaspect, user 112 may be a customer or potential customer of a merchantassociated with merchant device 120. For instance, user 112 may transactwith merchant device 120. In another aspect, user 112 may be a customerof the financial service provider associated with financial serviceprovider device 130. For instance, the financial service provider maymaintain a financial service account (e.g., checking account) for user112.

Merchant device 120 may be associated with a merchant, such as one ormore providers of goods and/or services, such as a retailer, etc.Merchant device 120 may include one or more computing systems that areconfigured to perform computer-implemented processes, such as a server,desktop, laptop, mobile device, embedded system or other dedicatedhardware, etc. Further, merchant device 120 may include one or morecomputing devices configured to process and handle purchase transactionsat a physical location of the associated merchant, such as point of saleterminals, local servers, kiosks, barcode scanners, etc., at a retailerlocation. Merchant device 120 may be configured to perform financialtransaction processes, such as receiving, processing, and handlingpurchase transactions, payment processes, etc. associated with the saleof goods and/or services provided by the associated merchant. In someaspects, merchant device 120 may include computing devices that mayinclude back and/or front-end computing components that store consumertransaction data and execute software instructions to perform operationsconsistent with the disclosed embodiments, such as computers that areoperated by employees of the associated merchant (e.g., back-officesystems, etc.).

In certain aspects, a customer associated with client device 110 (e.g.,user 112) may purchase goods and/or services from a merchant associatedwith merchant device 120. In some instances, the customer may use afinancial account provided by a financial service provider to pay forthe goods and/or services. In other instances, the customer may useanother payment method, such as cash.

Financial service provider device 130 may be associated with a financialservice provider. The financial service provider may be a bank, creditunion, credit card issuer, or other type of financial service entitythat generates, provides, manages, and/or maintains financial serviceaccounts for one or more users (e.g., user 112). Financial serviceaccounts may include, for example, checking accounts, savings accounts,credit card accounts, loan accounts, rewards accounts, and any othertypes of financial service account known to those skilled in the art.Financial service accounts may be associated with electronic accounts,such as a digital wallet or similar account that may be used to performelectronic transactions, such as purchasing goods and/or servicesonline. Financial service accounts may also be associated with physicalfinancial service account cards, such as a debit or credit card that auser may carry on their person and use to perform financial servicetransactions, such as purchasing goods and/or services at a point ofsale terminal (i.e., merchant device 120).

The financial service provider may include infrastructure and componentsthat are configured to generate and provide financial service accountsand financial service account cards (e.g., debit cards, credit cards,etc.). The financial service provider may also include infrastructuresand components that are configured to manage transactions associatedwith a customer financial service account. In certain aspects, financialservice provider device 130 may include one or more computing devicesconfigured to communicate with client device 110 and merchant device 120to via network 140 to execute processing steps associated with a pointof sale deposit. For example, financial service provider device 130 mayinclude one or more computing devices configured to generate deposittokens, authorize transactions, and settle accounts, as will bedescribed in more detail below.

In certain aspects, the financial service provider associated withfinancial service provider device 130 may be (or include a servicecorresponding to that of) a direct bank. The direct bank may maintainfinancial service accounts with customers, such as checking and savingsaccounts, in a manner known in the art. The direct bank, however, maynot include physical branch locations at which the customers may maketransactions, such as financial deposits or withdrawals, typicallyassociated with a bank or similar financial service provider. In otherwords, management of financial service accounts may take place remotely,such as via network 140.

Network 140 may be any type of network configured to providecommunications between components of system 100. For example, network140 may be any type of network (including infrastructure) that providescommunications, exchanges information, and/or facilitates the exchangeof information, such as the Internet, a Local Area Network, or othersuitable connection(s) that enables the sending and receiving ofinformation between the components of system 100. In other embodiments,one or more components of system 100 may communicate directly through adedicated communication link(s) (not shown), such as a link betweenclient device 110 and merchant device 120.

It is to be understood that the configuration and boundaries of thefunctional building blocks of system 100 has been defined herein for theconvenience of the description. Alternative boundaries can be defined solong as the specified functions and relationships thereof areappropriately performed. Alternatives (including equivalents,extensions, variations, deviations, etc., of those described herein)will be apparent to persons skilled in the relevant art(s) based on theteachings contained herein. For example, merchant device 120 may includefinancial service provider device 130 for performing operationsassociated with a private label financial account provided by a merchantassociated with merchant device 120. Such alternatives fall within thescope and spirit of the disclosed embodiments.

FIG. 2 shows an exemplary server 211 for implementing embodimentsconsistent with the present disclosure. Variations of server 211 may beused by client device 110, merchant device 120, and/or financial serviceprovider device 130.

In one embodiment, server 211 may include one or more processors 221,one or more memories 223, and one or more input/output (I/O) devices222. According to some embodiments, server 211 may include an embeddedsystem or similar computing device that generates, maintains, andprovides web site(s) consistent with disclosed embodiments. Server 211may be standalone, or it may be part of a subsystem, which may be partof a larger system. For example, server 211 may represent distributedservers that are remotely located and communicate over a network (e.g.,network 140) or a dedicated network, such as a LAN. Server 211 maycorrespond to any of client device 110, merchant device 120, andfinancial service provider device 130.

Processor 221 may include one or more known processing devices, such asa microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMD™, or any of variousprocessors manufactured by Sun Microsystems. The disclosed embodimentsare not limited to any type of processor(s) configured in server 211.

Memory 223 may include one or more storage devices configured to storeinstructions used by processor 221 to perform functions related todisclosed embodiments. For example, memory 223 may be configured withone or more software instructions, such as program(s) 224 that mayperform one or more operations when executed by processor 221. Thedisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, memory 223 mayinclude a single program 224 that performs the functions of the server211, or program 224 could comprise multiple programs. Additionally,processor 221 may execute one or more programs located remotely fromserver 211. For example, client device 110, merchant device 120, and/orfinancial service provider device 130, may, via server 211, access oneor more remote programs that, when executed, perform functions relatedto certain disclosed embodiments. Memory 223 may also store data 225that may reflect any type of information in any format that the systemmay use to perform operations consistent with the disclosed embodiments.

I/O devices 222 may be one or more devices configured to allow data tobe received and/or transmitted by server 211. I/O devices 222 mayinclude one or more digital and/or analog communication devices thatallow server 211 to communicate with other machines and devices, such asother components of system 100.

Server 211 may also be communicatively connected to one or moredatabase(s) 226. Server 211 may be communicatively connected todatabase(s) 226 through network 140. Database 226 may include one ormore memory devices that store information and are accessed and/ormanaged through server 211. By way of example, database(s) 226 mayinclude Oracle™ databases, Sybasem™ databases, or other relationaldatabases or non-relational databases, such as Hadoop sequence files,HBase, or Cassandra. The databases or other files may include, forexample, data and information related to the source and destination of anetwork request, the data contained in the request, etc. Systems andmethods of disclosed embodiments, however, are not limited to separatedatabases. In one aspect, system 200 may include database 226.Alternatively, database 226 may be located remotely from the system 200.Database 226 may include computing components (e.g., database managementsystem, database server, etc.) configured to receive and processrequests for data stored in memory devices of database(s) 226 and toprovide data from database 226.

FIG. 3 is a flowchart of an exemplary process 300 for executing a pointof sale deposit, consistent with disclosed embodiments. In some aspects,process 300 may take place in the context of a transaction between acustomer associated with client device 110 (e.g., user 112) and amerchant associated with merchant device 120. For example, user 112 maybe a customer that makes a purchase at a merchant associated withmerchant device 120. User 122 may be an employee of the associatedmerchant that operates merchant device 120 (e.g., a point of saledevice) to execute the transaction with user 112. User 112 maysupplement the purchase transaction with a point of sale deposittransaction, which may take place via process 300.

Process 300 may include client device 110 initiating a deposittransaction (step 310). For example, user 112 may operate client device110 to initiate the deposit transaction. Client device 110 may be amobile device (e.g., a smart phone), and user 112 may operate the mobiledevice to execute software instructions (e.g., a mobile application) toinitiate the deposit transaction. Client device 110 may send informationassociated with the initiated deposit transaction to financial serviceprovider device 130 (step 320). In some aspects, initiation of thedeposit transaction and transmission of the deposit transactioninformation to financial service provider device 130 may occur at anytime before or during the transaction process between user 112 and themerchant associated with merchant device 120.

Financial service provider device 130 may receive and process theinformation sent by client device 110 related to the initiated deposittransaction (step 330). Financial service provider device 130 may alsooperate in conjunction with client device 110 to transmit the deposittransaction information to merchant device 120. Subsequently, merchantdevice 120 may receive the deposit transaction information (step 340).In some embodiments, merchant device 120 may use the received deposittransaction information to add the deposit transaction to the purchasetransaction. In some aspects, the deposit transaction may be added bythe merchant device as a customer debit (i.e., the customer owes themerchant the deposit amount to settle the transaction). Alternatively,the deposit transaction may be added by the merchant device as acustomer credit (i.e., the merchant owes the deposit amount to thecustomer). In other embodiments, the deposit transaction may be the onlytransaction that takes place between user 112 and merchant device 120.

Merchant device 120 and financial service provider device 130 may workin conjunction to authorize the deposit transaction (step 350). Forexample, merchant device 120 and financial service provider device 130may communicate with each other via network 140 to authorize the deposittransaction or otherwise ensure that the deposit transaction is secureand not fraudulent, as further discussed below.

Merchant device 120 may also complete the deposit transaction and anyother concurrent transaction (e.g., purchase transaction) (step 360). Insome aspects, user 112 may pay the merchant to settle the amount owedfor the transaction(s). For example, user 112 may (in addition to payingfor any goods or services transactions) provide cash to the merchant inan amount equal to the amount being deposited through the deposittransaction. In other embodiments, user 112 may use another paymentmethod involving, for example, a financial account product (i.e., creditcard, debit card, mobile wallet, etc.) to settle the transaction(s).Merchant device 120 may notify financial service provider device 130that the deposit transaction has been completed (e.g., funds paid to themerchant), which may complete authorization and signal financial serviceprovider device 130 to transfer funds to the customer's financialaccount. Financial service provider device 130 may notify the customerthat the deposit transaction was successfully completed.

In addition, the merchant and financial service provider may completethe transaction by settling the amount owed to either entity (step 370).For example, the merchant device 120 may transfer to the financialservice provider device 130 an amount equal to the deposited amount. Theamount may be transferred in a manner known in the art, such as throughan automated clearing house. In this way, process 300 may allow a user112 to deposit cash into a financial service account with a financialservice provider through a deposit transaction with a merchant.

FIG. 4 is a flowchart of an exemplary process 400 by which client device110 may initiate, and/or be used to initiate, a point of sale deposit.User 112 may initiate a point of sale deposit at any time before orduring a corresponding transaction with a merchant (e.g., a merchantassociated with merchant device 120). For example, a user 112 mayinitiate a purchase transaction with a merchant and concurrently decideto initiate a deposit transaction with the same merchant. In otherwords, user 112 may transact with a merchant to purchase an item andmake a deposit into a financial service account (e.g., a checkingaccount).

To initiate the deposit transaction, client device 110 may receiveinformation about the deposit (step 410). The deposit information mayinclude details about the financial service account in which the depositwill be made, such as the financial service provider that maintains thefinancial service account and account identifiers (e.g., account name,type, number, etc.), details about the deposit itself, such as theamount of the deposit, a customer identifier (e.g., customer name,identification number, etc.), and details about the merchant at whichthe deposit transaction will take place, such as merchant name,location, and/or other merchant identifiers (e.g., store number).According to some embodiments, client device 110 may receive informationabout the deposit from data stored on a financial account product via,for example, card swipe, card insertion, near field communication, etc.

Client device 110 may receive deposit information as data input by user112. For example, user 112 may use an I/O device and/or a user interfaceassociated with client device 110 to enter deposit information. In someembodiments, client device 110 may be a mobile device configured toexecute software instructions to run a mobile application. The mobileapplication may be associated with the financial service provider thatmaintains the financial service account that will receive funds as aresult of the deposit transaction. In certain embodiments, the mobileapplication may be associated with a direct bank. User 112 may operateclient device 110 to execute software instructions to run the mobileapplication. The mobile application may be executed to display aninteractive user interface with which user 112 may direct client device110 to initiate the deposit transaction and prompt user 112 for depositinformation. User 112 may enter deposit information, such as byselecting a financial service account to receive the deposited funds andentering the amount to be deposited. Some deposit information, such asfinancial service provider and other financial service account detailsmay be automatically associated with the initiated deposit, such as viasoftware instructions associated with the mobile application.

User 112 may also input to client device 110 information related to themerchant at which the deposit will be occur. For example, user 112 maybe prompted to enter details about the merchant through a user interfaceassociated with client device 110 and the mobile application. In otherembodiments, the merchant information may be automatically acquired byclient device 110, such as through a GPS location function. Clientdevice 110 may include a GPS device configured to acquire currentlatitude and longitude of client device 110. For example, client device110 may include a GPS device that provides geographic locationinformation (not shown). In some embodiments, the GPS device maycommunicate with a GPS satellite navigation system that is used todetermine the precise location of client device 110. The GPS device maydecode time signal transmissions received from multiple satellites todetermine the position of client device 110 using, for example,trilateration techniques performed by a processor executing softwarestored on a memory device within the GPS device. Client device 110,therefore, may calculate and transmit geographic position information(e.g., location coordinates) associated with client device 110.

In some embodiments, determined location coordinates associated withclient device 110 may be stored as deposit information or additionalprocesses may be executed by client device 110 to determine a merchantassociated with the determined coordinates. For example, client device110 may execute a software process to determine a specific merchant froma database of possible merchants that is located at the determinedlocation coordinates. The determined merchant and any associatedinformation may be stored, marked, and/or labeled as depositinformation.

Client device 110 may send the received deposit information to financialservice provider device 130 (step 420). For example, client device 110may execute software instructions to send the received depositinformation to financial service provider device 130 via network 140. Inthe embodiment in which client device 110 is a mobile device, network140 may include a mobile network (i.e., a cellular data network).Financial service provider device 130 may be a computing device (e.g., aserver) configured to receive and process (or forward the information toanother computing device for processing) the deposit information.

As will be described in more detail below, financial service providerdevice 130 may execute a process to generate a deposit token associatedwith the deposit transaction. In process 400, client device 110 may beconfigured to receive the generated deposit token (step 430). Forexample, financial service provider device 130 may send the generateddeposit token via network 140, which may be received by client device110. The generated deposit token may be a representation of the deposittransaction, such as a unique alphanumeric identifier associated withthe deposit information.

Client device 110 may execute software instructions to process thereceived deposit token such that the deposit token may be transmitted tomerchant device 120. In some embodiments, client device 110 may processthe deposit token to generate a deposit code (step 440). The depositcode may be any type of representation of data that is in a formconvenient for use with merchant device 120, such as a readable code.For example, the deposit code may be a barcode that is configured to bedisplayed by a display device associated with client device 110. In theembodiment in which client device 110 is a mobile device, the barcodemay be displayed on a mobile device screen. The barcode may be encodedwith the deposit information (e.g., the deposit token). As will bedescribed in more detail below, merchant device 120 may read the depositcode (e.g., scan the barcode with a barcode scanner) such that therequisite deposit information may be transmitted to merchant device 120.

According to the steps of process 400, client device 110 may initiate apoint of sale deposit transaction. Process 400 includes steps thatinitiate the deposit transaction with financial service provider device130 (e.g., step 420) and arrange for the deposit transaction to beinitiated with merchant device 120 (e.g., step 440). In this way,additional processes may be executed to carry out and complete thedeposit transaction. In some embodiments, client device 120 maysubsequently receive a notification that the deposit transaction iscompleted (step 450).

FIG. 5 is a flowchart of an exemplary process 500 by which merchantdevice 120 may execute, and/or be used to execute, a point of saledeposit transaction. In certain aspects, merchant device 120 may executesoftware instructions to carry out some or all of the steps of process500. As described above with respect to process 400, process 500 may beexecuted in the context of a financial transaction between a customer(e.g., user 112) and a merchant (e.g., the merchant associated withmerchant device 120).

Consistent with disclosed embodiments, a transaction may be initiatedwith merchant device 120 (step 510). The initiated transaction mayinclude a deposit transaction, such as the deposit transaction describedabove with respect to process 400. The deposit transaction may be a partof, supplemental to, or take place individually from another transactionbetween the merchant and the customer. For example, the deposittransaction may be a part of a purchase transaction between a customerand a retailer merchant. In these exemplary embodiments, the purchasetransaction may be initiated with merchant device 120 in a typicalmanner known in the art. For example, merchant device 120 may be a pointof sale register with a barcode scanner and user 122 (e.g., a merchantemployee) may scan a barcode associated with the item to be purchased bythe customer with the barcode scanner. Merchant device 120 may executesoftware instructions to decode the barcode to, among other things,identify an amount owed by the customer to the merchant for the item. Inthis way, the transaction may be initiated with merchant device 120.

It should be understood that, in some embodiments, the transactionbetween the customer and the merchant may consist only of a point ofsale deposit transaction. In these embodiments, step 510 may includeother steps to initiate the transaction, such as receiving data inputfrom user 122 to signal that a deposit transaction is being initiated.In other embodiments, step 510 may not be included in process 500, andstep 520, described in more detail below, may initiate the deposittransaction with merchant device 120.

Process 500 may further include merchant device 120 receiving deposittransaction information (step 520). The deposit transaction informationmay include information from client device 110 and/or financial serviceprovider device 130. For example, in the embodiment in which clientdevice 110 is a mobile device that generates a barcode from a deposittoken received from financial service provider device 130 (e.g., step440 of process 400), merchant device 120 may receive deposit informationby decoding the information encoded by the barcode. For example, user122 may use a barcode scanner to scan a barcode generated and displayedby client device 110. Merchant device 120 may execute softwareinstructions to extract the deposit information from the encodedinformation. In this way, merchant device 120 may store and/or processthe deposit information to continue process 500.

While a barcode has been described in the above exemplary embodiment, itshould be understood that any method or means of relaying encodeddeposit information may be used (e.g., OR code, word or picturerecognition software, etc.). In other embodiments, merchant device 120may receive deposit information in a manner other than through areadable medium. For example, instead of a barcode, client device maygenerate an alphanumeric code as the deposit code. User 122 may enterthe alphanumeric code to merchant device 120, such as through an I/Odevice and/or a user interface. Merchant device 120 may be programmedwith software instructions (e.g., a software application) configured toprocess the alphanumeric code to determine the deposit transactioninformation associated with that particular alphanumeric code. In stillother embodiments, communication signals between client device andmerchant device 120 may be used, such as wireless signals, Bluetooth,etc.

In some embodiments, merchant device 120 may receive deposit informationfrom a source other than client device 110. In some aspects, the depositinformation received from a source other than client device 110 mayinclude information in addition to information from client device 110.For example, user 112 may inform user 122 that they wish to initiate adeposit transaction. User 122 may input information through an I/Odevice and/or a user interface, such as an amount that will be depositedthrough the deposit transaction. In other embodiments, merchant device120 may receive the deposit information from user 112. User 112 mayenter deposit information into an I/O device and/or user interfaceassociated with merchant device 120. User 112 may enter the depositinformation manually (e.g., entering an amount via a keypad) and/orautomatically (e.g., swiping a debit card to transmit financial serviceaccount information). In any instance, merchant device 120 may storeand/or process the received deposit information to continue process 500.

Merchant device 120 may also seek to authorize the deposit transactionwith the financial service provider (step 530). For example, merchantdevice 120 may send an authorization request to financial serviceprovider device 130. Merchant device 120 may send the authorizationrequest via network 140. In some embodiments, the authorization requestmay include transmitting the deposit token to financial service providerdevice 130.

As will be described in more detail below, financial service providerdevice 130 may receive the authorization request and make adetermination based on the information in the request and otherinformation about the deposit transaction (e.g., information receivedfrom client device 110) regarding whether the deposit transaction isauthorized to continue. In other embodiments, merchant device 120 mayattempt to authorize the deposit transaction by prompting user 112 oruser 122 to enter additional information. For example, merchant device120 may request that user 112 swipes a debit card associated with thefinancial service account to which funds are to be deposited.

Merchant device 120 may determine whether the deposit transaction hasbeen authorized (step 540). For example, merchant device 120 may receivea notification from financial service provider device 130 withinformation related to the result of the authorization determination. Insome embodiments, the notification may include deposit information(e.g., deposit amount and a customer identifier, such as the customer'sfirst name). In addition, the notification may include a verificationcode. The verification code may be a unique identifier (e.g.,alphanumeric code) generated by financial service provider device 130and related to the deposit transaction.

In other embodiments, merchant device 120 may determine authorizationthrough information received from user 112 and/or user 122. For example,merchant device 120 may execute software instructions to processinformation from a debit card swiped by user 112 to determine if thedeposit transaction is authorized (e.g., deposit information receivedfrom client device 110 matches information obtained from the debitcard). In these exemplary embodiments, process 500 may include anadditional step of sending a notification to financial service providerdevice 130 that the deposit transaction was authorized.

If merchant device 120 receives authorization to continue the deposittransaction, merchant device 120 may add the deposit transaction andcomplete the overall transaction with the customer (step 550). Forexample, merchant device 120 may add the amount of the deposit(extracted from deposit information) to an amount owed to the merchantassociated with merchant device 120. In the embodiment in which thedeposit transaction is part of an overall transaction that includes apurchase transaction, the amount of the deposit may be added to theamount of the purchase(s) to determine a total amount that is owed tothe merchant by the customer (e.g., user 112).

Merchant device 120 may receive information indicating that the customerhas paid the amount owed to the merchant. For example, the customer(e.g., user 112) may pay cash to the merchant and user 122 may enter theamount paid by the customer to merchant device 120. Merchant device 120may subsequently transmit a notification to financial service providerdevice 130 notifying the financial service provider that the customerhas transferred the funds (e.g., cash) to the merchant for the deposittransaction (step 560). The notification may include, for example, thedeposit token and the verification code, which may allow financialservice provider device 130 to complete authorization of thetransaction.

Merchant device 120 may execute additional software instructions tocomplete the transaction, which may include producing a receipt. Afterprocess 500 is finished, the transaction between the customer andmerchant may be completed and the funds previously held by the customermay be available or eventually become available (such as aftersettlement between the merchant and financial service provider) as fundsdeposited into the financial service account.

FIG. 6 is a flowchart of an exemplary process 600 by which financialservice provider device 130 may execute a point of sale deposit. Process600 includes steps that, when executed in conjunction with some or allof the steps of processes 400 and 500 described above, complete a pointof sale deposit by a customer associated with client device 110 with amerchant associated with merchant device 120.

Process 600 includes financial service provider device 130 receiving arequest to initiate a deposit transaction and/or deposit information(step 610). Step 610 may correspond to step 420 of process 400, in thatfinancial service provider device 130 may receive deposit informationsent from client device 110. Financial service provider device 130 mayuse the received deposit information to initiate the deposittransaction. For example, financial service provider device 130 may be acomputing device (e.g., an embedded system or other dedicated hardware)configured to execute software instructions to read and/or decode thereceived deposit information and associate the deposit transaction witha customer profile. For example, financial service provider device maydetermine the customer and financial service account to which funds areto be deposited, such as by searching a customer profile database tomatch received identifiers (e.g., account number).

Financial service provider device 130 may also process the depositinformation to generate a deposit token (step 620). For example,financial service provider device 130 may include a computing deviceconfigured to execute software instructions to run an applicationprogramming interface (API) to generate the deposit token. As describedabove, in some embodiments, the deposit token may be a uniquealphanumeric identifier associated with the deposit information. Thedeposit information associated with the generated deposit token may bestored by financial service provider device 130, such as in a system ofrecord. In other embodiments, the deposit token may additionally oralternatively include encoded deposit information received from clientdevice 110 (e.g., deposit amount, customer information, and/or merchantinformation) and/or additional information from the financial serviceprovider. After the deposit token is generated, financial serviceprovider device 130 may transmit the deposit token to client device 110(step 630), such as for use in processes 400 and 500.

In addition to generating the deposit token, financial service providerdevice 130 may continue processing of the initiated deposit transactionby creating a pending transaction. Financial service provider device 130may create a wash account that contains an amount equal to the depositamount (step 640). In some aspects, the wash account may be anintermediary financial account or other temporary placeholder for thefunds to be deposited into the customer's financial service account.Financial service provider device 130 may wait for additionalinformation before continuing processing of the deposit transaction.

Financial service provider device 130 may receive the above-mentionedadditional information in the form of an authorization request frommerchant device 120 (step 650). Step 650 may correspond to step 530 ofexemplary process 500. For example, merchant device 120 may seek toauthorize the deposit transaction by sending the authorization requestwith deposit information (e.g., the deposit token and wash accountdetails) through network 140. In some aspects, the authorization requestmay be a notification sent and received through existing paymentchannels between the merchant and financial service provider. Forexample, the request may be sent and received via credit/debit cardprocessing protocols, with the deposit information encoded into thecommunication, such as in a discretionary data field. In someembodiments, authorization requests sent between merchant device 120 andfinancial service provider device 130 may include processing through anAPI. In any instance, financial service provider device 130 may processthe received authorization request to determine if the deposittransaction should be authorized (step 660). For example, financialservice provider device 130 may determine if the received depositinformation (from merchant device 120) matches the deposit informationassociated with the pending transaction (e.g., received deposit tokenmatched generated deposit token). In addition, financial service device130 may determine a merchant associated with merchant device 120 andattempt to match the determined merchant to a merchant associated with amerchant location received from client device 110. If the merchantsmatch, the deposit transaction may be authorized.

If the deposit transaction is not authorized (step 660; NO), process 600may stop (step 670). In some embodiments, financial service providerdevice 130 may leave the deposit transaction pending to await anotherauthorization request. If, after a certain period of time, anotherrequest is not received, the pending deposit transaction may expire.

If the deposit transaction is authorized (step 660; YES), financialservice provider device 130 may authorize the transaction with merchantdevice 120 (step 675). For example, financial service provider device130 may transmit a notification to merchant device 120. As describedabove with respect to step 540 of process 500, the notification mayinclude deposit information and a verification code. After transmittingthe notification, financial service provider device 130 may receive anotification in return from merchant device 120. The notification frommerchant device 120 may include the deposit token and the verificationcode, for example, which may inform the financial service provider thatthe customer has transferred funds (e.g., cash) in the amount of thedeposit to the merchant.

Receipt of the return notification from merchant device 120 may completeauthorization of the deposit transaction. With the transactionauthorized, financial service provider device 130 may transfer the fundsin the wash account to the chosen customer financial service account(step 680). In this way the wash account may be “settled,” and thedeposited funds may become available to the customer in the receivingaccount. Financial service provider device 130 may complete the deposittransaction by marking the pending transaction as complete and notifyingthe customer that the transaction is complete (step 690). In someembodiments, financial service provider device 130 may transmit amessage (e.g., sms text message, push notification, email) to clientdevice 110 to notify the customer.

Additional processes may occur between financial service provider andthe merchant to settle the amount owed to either entity. For example,the financial service provider may receive funds from the merchant tosettle the amount of the deposit that was given to the merchant by thecustomer. Settlement may occur in a manner known in the art, such asthrough an automated clearing house. Either or both of merchant device120 and financial service provider device 130 may execute steps thatlead to settlement. If any of the steps of the above-described processesfail (e.g., network outage, hardware failure, fraud detection, etc.),the process(es) may be stopped. If the deposit transaction is alreadypending at the point of stoppage, the deposit transaction may remainpending and wait for the respective process to complete. If, after acertain period of time, the deposit transaction process fails tocontinue or complete, the pending transaction may expire and the depositcancelled.

In addition, it should be understood that other entities, such as themerchant's financial service provider, payment processors, etc., mayinclude devices that execute one or more of the steps of the processesdescribed herein.

Further, it should be understood that any of client device 110, merchantdevice 120, and financial service provider device 130, while representedas a single device, may be multiple devices that work individually or inconcert to execute the steps of the processes described herein. Forexample, financial service provider device may include a computingdevice that includes the API that generates and transmits the deposittoken and a separate computing device that authorizes the deposittransaction and settles the wash account. Other arrangements andconfigurations of devices may be possible.

Using the above-described processes, a customer of a financial serviceprovider may execute a point of sale deposit in the form of a mobilecash deposit. The deposit transaction may be used to deposit funds(e.g., cash) to a financial service account using client device 110 incoordination with a merchant device 120. In this way, the disclosedsystems may provide more efficient deposit transactions, allowingcustomers to make deposits while also completing other transactions.

In certain aspects, the disclosed embodiments provide incentives formerchants to work with financial service providers to present point ofsale deposits to customers. For example, a merchant may partner with afinancial service provider to offer point of sale deposits at theirmerchant locations.

While the above processes have been described with regard to point ofsale deposits at merchants, it should be understood that similarprocesses may be used for other financial transactions. For example,consistent with disclosed embodiments, system 100 may be used to makebill payments in cash. In certain aspects relating to these embodiments,the disclosed embodiments may be configured to perform one or more ofthe process steps described above, however, for example, instead oftransferring funds from the wash account to a financial service accountassociated with the user, financial service provider device 130 maytransfer the funds to another system (e.g., third-party system) to paythe bill.

Other alternatives may include replacing merchant device 120 withanother device, such as a bank branch device located on or near themerchant's premises. The bank branch device may be associated with afinancial service provider (which may not be the same financial serviceprovider with which the customer has a financial service account). Inthis way, the customer may make a deposit into their financial serviceaccount at a bank branch (even though the bank branch may not be theirfinancial service provider).

In another example, merchant device 120 may be an ATM machine. The ATMmachine may be configured to operate in substantially the same manner asmerchant device 120. For instance, the ATM machine may be capable ofreading a barcode generated by client device 110, authorizing thedeposit transaction with financial service provider device 130, andreceiving the cash to complete the transaction. The exemplary disclosedembodiments describe systems and methods for point of sale deposits atmerchant locations. The foregoing description has been presented forpurposes of illustration. It is not exhaustive and is not limited to theprecise forms or embodiments disclosed. Modifications and adaptations ofthe embodiments will be apparent from consideration of the specificationand practice of the disclosed embodiments. For example, the describedimplementations include hardware and software, but systems and methodsconsistent with the present disclosure can be implemented as hardwarealone.

In addition, in alternative embodiments, certain additional oralternative components and/or processes may be implemented to providethe point of sale deposits. For example, in some alternativeembodiments, another device may perform some or all of the operationsconsistent with the above described embodiments other than the merchantdevice and/or financial service provider device. For instance, athird-party device may perform one or more processes in conjunction withone or more of the devices described above. An exemplary embodiment forproviding point of sale deposits that includes a third-party device isdescribed in more detail below.

FIG. 7 is a block diagram illustrating an exemplary system 700 forperforming one or more operations, consistent with the disclosedembodiments. System 700 may be similar to system 100, including one ormore of the same or similar components for performing one or more of thesame or similar processes described above, and one or more additional oralternative components for performing one or more additional oralternative processes. For example, in one embodiment, system 700 mayinclude client device 110, merchant device 120, financial serviceprovider device 130, third-party device 750, and network 140. It shouldbe understood that the above descriptions of client device 110, merchantdevice 120, financial service provider device 130, and network 140provided with respect to system 100 may apply equally to system 700.User 112 and user 122 may be similarly associated with client device 110and merchant device 120, respectively, as described above.

Third-party device 750 may be one or more computer systems associatedwith a third-party. Third-party device 750 may include one or morecomputing systems that are configured to perform computer-implementedprocesses, such as a server, desktop, laptop, mobile device, embeddedsystem or other dedicated hardware, etc. For example, third-party device750 may include some or all of the components of server 211.

Third-party device 750 may be associated with an entity that maytransact with a customer, merchant, and/or financial service provider.For example, third-party device 750 may be associated with an entitythat includes one or more transaction processing devices configured toperform one or more processes to receive a payment, deliver a payment,and/or process a payment to or from a customer, merchant, or financialservice provider.

In an exemplary embodiment, third-party device 750 may be configured togenerate and/or provide a financial account for a customer. For example,third-party device 750 may be associated with a financial accountprovider, and configured to generate and/or provide a financial accountfor a customer. In some embodiments, the financial account may be atemporary account that is associated with a customer based on a fundingof the temporary account. For instance, third-party device 750 may beassociated with a purchasing card provider (e.g., gift card provider),which may provide a purchasing card account to a customer based on acustomer purchase of a purchasing card. The purchasing card account maybe usable by the customer to fund future transactions, such astransactions associated with a merchant associated with the purchasingcard (e.g., a retail store gift card redeemable at the retail store). Itshould be understood, however, that the third-party associated withthird-party device 750 may provide any type of financial account, whichmay or may not be temporary or limited accounts that are similar tothose associated with purchasing cards.

Further, the third-party associated with third-party device 750 mayprovide financial accounts that are associated with electronic accountproducts, such as a virtual purchasing card account that may be usedthrough a client device, such as a mobile application executed by amobile device. Financial service accounts may also be associated withphysical financial account cards, such as a purchasing cards (e.g., giftcards) that a user may carry on their person and use to performfinancial transactions, such as purchasing goods and/or services at apoint of sale terminal (i.e., merchant device 120).

In certain aspects, third-party device 750 may include one or morecomputing devices configured to communicate with client device 110,merchant device 120, and financial service provider device 130 vianetwork 140, and may be configured to execute processing stepsassociated with a point of sale deposit. For example, third-party device750 may be configured to generate and provide a temporary purchasingcard account to perform a point of sale deposit by funding the temporarypurchasing card account and immediately transferring the received fundsto a financial service provider account. As will be described in moredetail below, third-party device 750 may include one or more computingdevices configured to generate temporary financial accounts, generatetransaction tokens, and settle accounts.

FIG. 8 is a flowchart of an exemplary process 800 for executing a pointof sale deposit, consistent with disclosed embodiments. In some aspects,process 800 may take place in the same context as process 300 describedabove. In particular, process 800 may take place in the context of atransaction between a customer associated with client device 110 (e.g.,user 112) and a merchant associated with merchant device 120. Forexample, user 112 may be a customer that makes a purchase at a merchantassociated with merchant device 120. User 122 may be an employee of theassociated merchant that operates merchant device 120 (e.g., a point ofsale device) to conduct the transaction with user 112. User 112 maysupplement the purchase transaction with a point of sale deposittransaction, which may take place via process 300. It should beunderstood, however, that the transaction between user 112 and themerchant may include only a point of sale deposit (e.g., no additionalpurchases or other transactions).

Further, in some instances, merchant device 120 may be configured suchthat it does not recognize the point of sale deposit as a deposittransaction. The same may be true for the merchant associated withmerchant device 120. Instead, the disclosed embodiments may beconfigured to perform operations in process 800 such that it appears tothe merchant device 120 and the merchant that a customer is buying apurchasing card (e.g., gift card), which may be a virtual gift card onclient device 110. In this way, merchant device 120 may performoperations for completing a purchase while other components of system700 may perform operations that complete the deposit transaction. Thus,in certain embodiments, merchant devices 120 (e.g., conventional pointof sale devices) may participate in point of sale deposit transactionswithout substantial modification.

In one embodiment, process 800 may include client device 110 initiatinga deposit transaction (step 810). For example, client device 110 mayinitiate the deposit transaction based on input from user 112. Clientdevice 110 may be a mobile device (e.g., a smart phone), and the mobiledevice may execute software instructions (e.g., a mobile application) toinitiate the deposit transaction based on input from user 112 through auser interface (e.g., touchscreen). In order to initiate the deposittransaction, client device 110 may receive a deposit amount (e.g., anamount of funds to be deposited) and a financial service account toreceive the deposit.

Third-party device 750 may receive and process transaction information(step 820). For example, client device 110 may transmit transactioninformation to third-party device 750 via network 140 after the deposittransaction is initiated. In some embodiments, client device 110 maytransmit information to third-party device 750 through a transactionAPI, which may be associated with financial service provider device 130.Third-party device 750 may generate a temporary financial account (orother type of account, etc.) for use in the deposit transaction,consistent with the disclosed embodiments. Third-party device 750 mayprovide information associated with the temporary financial account toclient device 110 and/or financial service provider 130. For example,third-party device 750 may generate a transaction token and send thetransaction token to client device 110 (e.g., via the transaction API).The transaction token may include authorization information, which mayinclude a transaction identifier (e.g., a unique alphanumeric code), thedeposit amount, information identifying the temporary financial accountgenerated by third-party device 750, and/or other information associatedwith the transaction.

Financial service provider device 130 may also receive and processdeposit transaction information (step 830). For example, client device110 may transmit transaction information to financial service providerdevice 130 after, concurrently, or before communicating with third-partydevice 750. Alternatively, third-party device 750 may transmittransaction information to financial service provider device 130, suchas, for example, after receiving the information from client device 110.In some embodiments, financial service provider device 130 may receivethe transaction information via the transaction API. In one embodiment,the transaction information includes the transaction token. Financialservice provider device 130 may execute software that performsoperations that generate a pending transaction associated with thefinancial service account that will be receiving the deposit.

Merchant device 120 may also receive and process transaction information(step 840). For example, merchant device 120 may receive transactioninformation through a point of sale device (e.g., register, terminal,etc.). Merchant device 120 may receive the transaction information asinformation associated with the purchase of a purchasing card (e.g.,gift card). For example, client device 110 may generate an opticalrepresentation (e.g., barcode, OR code, etc.) of data associated with atemporary financial account (e.g., a virtual gift card). Merchant device120 may scan the optical representation to receive the data and performone or more operations based on the data to perform a purchasetransaction associated with the temporary financial account (e.g., addpurchase of a gift card to a list of transactions between the customerand the merchant). In one embodiment, the data received by merchantdevice 120 may include the transaction token.

User 112 may pay the merchant to settle the amount owed for thetransaction(s). For example, user 112 may (in addition to paying for anygoods or services transactions) provide cash to the merchant in anamount equal to the amount being deposited through the deposittransaction. In other embodiments, user 112 may use another paymentmethod involving, for example, a financial account product (i.e., creditcard, debit card, gift card, mobile wallet, etc.) to settle thetransaction(s). It should be understood that user 112 may pay with anytype of currency, including purchasing cards (e.g., gift cards) whichmay or may not be redeemable at the merchant associated with merchantdevice 120, virtual currency, etc. In process 800, merchant device 120may receive a notification that the customer has transferred funds tothe merchant (step 850). For example, merchant device 120 may receive anotification that the customer has paid based on user input (e.g.,keypad input from user 122, input from a credit/debit card terminal,etc.)

Third-party device 750 may receive information indicating that that thefunds have been transferred to the merchant (step 860). For example,merchant device 120 may transmit information to third-party device 750indicating that the transaction token was received and funds have beentransferred to the merchant (e.g., based on the notification received instep 850). Third-party device 750 may then activate and/or fund thetemporary financial account. In certain aspects, third-party device 750may provide information to financial service provider device 130indicating that the temporary financial account was funded and/oractivated (step 870). For example, third-party device 750 may notifyfinancial service provider device 130 via the transaction API.

Financial service provider device 130 may perform operations to completethe deposit transaction (step 880). For example, financial serviceprovider device 130 may release the pending transaction to transferfunds equal to the deposit amount into the financial service account.

In some embodiments, financial service provider device 130 may performoperations that generate an indication that the funds have beentransferred and thus a deposit transaction was successful. Further, incertain aspects, financial service provider device 130 may performoperations that generate and provide a notification that notifies clientdevice 110 that the deposit transaction was successfully completed (step890).

Third-party device 750 may deactivate the temporary financial accountsuch that it is no longer usable. For example, third-party device 750may delete information associated with the temporary financial account,such as the transaction token. Third-party device 750 may retain someinformation as a record of the transaction. In other embodiments, thetemporary financial account may remain active (e.g., to be used infuture deposit transactions).

After financial service provider device 130 makes the funds available tothe customer, the deposit transaction may be considered complete.However, the merchant, third-party, and financial service provider mayproceed to settle an amount owed to each other. In certain aspects,merchant device 120, third-party device 750, and financial serviceprovider device 130 may communicate with each other and/or othercomponents to perform operations that cause a fund transfer from themerchant to the third-party in an amount equal to the deposit amount.Third-party device 750 (or another device) may perform operations thattransfer the same amount to financial service provider device 130. Incertain embodiments, third-party device 750 and merchant device 120 maybe configured to execute software to perform transfer operations in amanner known in the art, such as through an automated clearing house.

Settlement completes the transfer of funds from a customer to amerchant, to a third-party, and finally to a financial service provider.Thus, in certain embodiments, process 800 may allow cash deposits (orother currency) to be performed into a financial service accountassociated with a financial service provider through a transaction witha merchant, by way of a third-party.

In certain aspects, the disclosed embodiments may be configured toprovide deposit transactions in a manner similar to conventionalpurchase transactions that occur between a customer and a merchant. Forexample, in certain embodiments, the third-party associated withthird-party device 750 may be a purchasing account card provider, andone or more operations performed by merchant device 120 may besubstantially the same as those that would take place during a normalpurchase transaction of a purchasing account card (e.g., gift card).

FIG. 9 is a flowchart of an exemplary client device point of saledeposit process 900, consistent with disclosed embodiments. Forinstance, user 112 may initiate a point of sale deposit at any timebefore or during a corresponding transaction with a merchant (e.g., amerchant associated with merchant device 120). For example, a user 112may initiate a purchase transaction with a merchant and concurrentlydecide to include a deposit transaction with the same merchant. Forinstance, through certain aspects of the disclosed embodiments, user 112may transact with a merchant to purchase an item and make a deposit intoa financial service account (e.g., a checking account). Client device110 may initiate a deposit transaction based on input from user 112prior to the transaction with the merchant. In this way, process 900 maybe similar to process 400 described above. However, process 900 mayinclude operations that involve third-party device 750 to initiate thedeposit transaction, as described below.

To initiate the deposit transaction, client device 110 may receiveinformation about the deposit transaction (step 910). The transactioninformation may include details about the financial service account inwhich the deposit will be made, such as the financial service providerthat maintains the financial service account and account identifiers(e.g., account name, type, number, etc.), details about the deposititself, such as the amount of the deposit, and details about themerchant at which the deposit transaction will take place, such asmerchant name, location, and/or other merchant identifiers (e.g., storenumber). According to some embodiments, client device 110 may receiveinformation about the deposit from data stored on a financial accountproduct via, for example, card swipe, card insertion, near fieldcommunication, etc. In other embodiments, user 112 may enter theinformation through a user interface displayed by software executed byclient device 110.

Client device 110 may receive deposit information as data input by user112. For example, user 112 may use an I/O device and/or a user interfaceassociated with client device 110 to enter deposit information. Forinstance, client device 110 may be a mobile device configured to executesoftware instructions to run a mobile application. The mobileapplication may be associated with the financial service provider thatmaintains the financial service account that will receive funds as aresult of the deposit transaction. In certain embodiments, the mobileapplication may be associated with a direct bank. Client device 110 mayexecute software instructions to perform operations associated with themobile application. The mobile application may be configured to generatefor display an interactive user interface that user 112 may provideinput that directs client device 110 to initiate the deposittransaction. The mobile application may also prompt user 112 for depositinformation. User 112 may enter deposit information, such as byselecting a financial service account to receive the deposited funds andentering the amount to be deposited. Client device 110 may automaticallyassociate some deposit information, such as financial service providerand other financial service account details, with the initiated deposit.For example, client device may execute the mobile application that isconfigured with default settings that perform one or more suchoperations based on received information, such as the depositinformation, etc.

Client device 110 may also send the transaction information tothird-party device 750 (step 920). For example, client device 110 mayexecute software instructions to send the received transactioninformation to third-party device 750 via network 140. In embodimentswhere client device 110 is a mobile device, network 140 may include amobile network (i.e., a cellular data network). Third-party device 130may be a computing device (e.g., a server, which may be a dedicatedserver) configured to receive and process (or forward the information toanother computing device for processing) the transaction information. Insome embodiments, client device 110 may send the transaction informationto third-party device 750 via a transaction API. Financial serviceprovider device 130 may include the transaction API.

The transaction information sent to third-party device 750 may identifythat client device 110 is attempting to initiate a deposit transactionwith a financial service provider through the third-party device 750.The transaction information may include the deposit amount, thefinancial service provider, and the financial service account that willreceive the deposit.

Third-party device 750 may execute a process to generate a temporaryfinancial account and a transaction token to be associated with thedeposit transaction. In process 900, client device 110 may be configuredto receive the transaction token (step 930). For example, third-partydevice 750 may send the generated transaction token via network 140(e.g., via the transaction API), which may be received by client device110. The generated transaction token may be a representation of thedeposit transaction and include authorization information, such as atransaction identifier, the deposit amount, information identifying thetemporary financial account generated by third-party device 750, and/orother information associated with the transaction.

Client device 110 may also send transaction information to financialservice provider device 130 (step 940). For example, client device 110may execute software instructions to send the transaction information(e.g., deposit amount and financial service account to receive thedeposit) to financial service provider device 130 via network 140 (e.g.,via the transaction API). In an exemplary embodiment, client device 110may also transmit the transaction token to financial service providerdevice 130. Financial service provider device 130 may create a pendingtransaction based on the received deposit information.

Client device 110 may execute software instructions to process thetransaction token such that transaction information may be transmittedto merchant device 120. In some embodiments, client device 110 mayprocess the transaction token to provide a transaction token to merchantdevice 120 (step 950). The transaction token provided to merchant devicemay be the same or different than the transaction token received fromthird-party device 750, and may include the transaction identifier, thedeposit amount, information identifying the temporary financial accountgenerated by third-party device 750, and/or other information associatedwith the transaction.

In one example, client device 110 may provide the transaction tokenthrough an optical representation (e.g., barcode, QR code, etc.) thatclient device 110 is configured to display. Client device 110 maydisplay the optical representation on a display device screen. Merchantdevice 120 may read the optical representation (e.g., scan a barcodewith a barcode scanner) such that merchant device 120 may receive thedata associated with the transaction token. In this way, merchant device120 may receive the transaction token from client device 110. In otherembodiments, client device may transmit the transaction token tomerchant device 120 (e.g., via network 140).

Merchant device 120, third-party device 750, and financial serviceprovider device 130 may communicate with each other and performadditional operations to complete the deposit transaction. In someembodiments, client device 120 may subsequently receive a notificationthat the deposit transaction is complete and that the deposited fundsare available (step 960). For example, financial service provider device130 may send a text message, push notification, email, etc., via thetransaction API.

FIG. 10 is a flowchart of an exemplary third-party point of sale depositprocess 1000, consistent with disclosed embodiments. Process 1000 mayinclude third-party device 750 receiving a request to initiate a deposittransaction and/or deposit transaction information (step 1010). Forexample, third-party device 750 may receive transaction information sentfrom client device 110 (e.g., step 920 of process 900), which may besent and received via the transaction API.

Third-party device 750 may use the received deposit information toinitiate the deposit transaction. For example, third-party device 750may generate a temporary financial account based on the received depositinformation (step 1020). The temporary financial account may be apurchasing card account (e.g., gift card account), or any other type offinancial account. Third-party device 750 may also generate thetransaction token, which may retain authorization information, such asthe transaction identifier, deposit amount, information identifying thetemporary financial account generated by third-party device 750, and/orother information associated with the transaction (as described above).The transaction identifier may be a unique alphanumeric code that may beused to identify the deposit transaction.

Third-party device 750 may transmit information associated with thetemporary financial account to client device 110 (step 1030). Forexample, third-party device 750 may transmit the transaction token toclient device 110 (e.g., via the transaction API). The transaction tokenmay include information sufficient to allow client device 110 togenerate an optical representation of the transaction token, asdescribed above.

Third-party device 750 may activate the temporary financial account(step 1040). For example, third-party device 750 may receive informationfrom merchant device 120 identifying the deposit transaction andindicating that the customer has transferred funds to the merchant. Theinformation may include at least some information from the transactiontoken (e.g., the transaction identifier), which the merchant devicereceived from client device 110 (e.g., via the optical representation).Third-party device 750 may match the transaction token to a storedtransaction token to identify the transaction and authorize activationof the temporary financial account.

In one embodiment, merchant device 120 and third-party device 750 maycommunicate to activate the temporary financial account using gift cardactivation protocols, processes, etc., that have been configured toallow activation of the temporary financial account. Activation mayinclude third-party device 750 assigning funds to the temporary account(e.g., funds equal to the deposit amount).

After the temporary financial account has been activated, third-partydevice 750 may transmit information to financial service provider device130 indicating that the temporary financial account was activated (step1050). For example, third-party device 750 may transmit the transactiontoken to financial service provider device 130 (e.g., via thetransaction API). As will be described, financial service providerdevice 130 may use the transaction token to complete the deposittransaction.

Third-party device 750 may receive a notification from financial serviceprovider device 130 that the transaction token was received and that thedeposit transaction was completed (step 1060). Third-party device 750may deactivate the temporary financial account based on thisnotification (step 1070). For example, third-party device 750 may removethe funds from the temporary financial account and delete thetransaction token. In some embodiments, third-party device 750 mayretain some information as a record of the transaction. In alternativeembodiments, third-party device 750 may maintain the temporary financialaccount for future use in deposit transactions (e.g., a dedicatedfinancial account that is used for point of sale deposits).

In an exemplary embodiment, the third-party may settle with the merchantand the financial service provider (e.g., after the deposit iscompleted, in advance of the deposit, etc.). Settlement may include thethird-party settling with the merchant to cover the funds that wereplaced into the temporary financial account based on the customer payingthe merchant. Settlement may also include the third-party settling withthe financial service provider to cover the deposit of funds into thefinancial service account. Third-party device 750 may execute softwareinstructions to perform one or more operations to cause the transfer offunds.

FIG. 11 is a flowchart of an exemplary financial service provider devicedeposit completion process 1100, consistent with disclosed embodiments.In one embodiment, financial service provider device 130 may executesoftware instructions to perform process 1100 to complete a deposittransaction.

Financial service provider device 130 may receive deposit transactioninformation (step 1110). For example, financial service provider device130 may receive deposit information from client device 110 (e.g., viathe transaction API), including deposit amount and the financial serviceaccount to receive the deposit. Financial service provider device 130may also receive from client device 110 the transaction token that wasgenerated by third-party device 750 and sent to client device 110.

Financial service provider device 130 may use the deposit information tocreate a pending deposit transaction associated with the financialservice account included in the deposit information (step 1120). Forexample, financial service provider device 130 may place funds into awash account.

Financial service provider device 130 may thereafter receive anindication that the deposit transaction should be completed. Inparticular, financial service provider device 130 may receive thetransaction token from third-party device 750 (step 1130). Third-partydevice 750 may send the transaction token to financial service providerdevice 130 (e.g., via the transaction API) based on receipt of anotification that the funds were transferred to the merchant (e.g., step1050 of process 1000).

Financial service provider device 130 may match the transaction tokenreceived from third-party device 750 with the transaction tokenpreviously received from client device 110 (step 1140). For example,third-party device 750 may match transaction identifiers that wereincluded with each received transaction token. The match may indicatethat the initiated deposit transaction is authorized and should becompleted. Financial service provider device 130 may thereafter completethe deposit transaction (step 1150). For example, financial serviceprovider device 130 may complete the generated pending transaction totransfer funds equal to the deposit amount from the wash account intothe selected financial service account. In this way, the funds may beavailable to the customer through the financial service account.

Financial service provider device 130 may send a notification tothird-party device 750 (e.g., via the transaction API) that notifiesthird-party device 750 that the deposit transaction was completed (step1160). Third-party device 750 may deactivate the temporary financialaccount based on the notification (e.g., step 1070 of process 1000). Insome embodiments, financial service provider device 130 may also send anotification to client device 110 to notify the customer (e.g., user112) that the deposit transaction is complete and/or that the funds areavailable in the financial service account (e.g., via the transactionAPI).

After the deposit transaction is completed, the financial serviceprovider associated with financial service provider device 130 maysettle an amount owed by the third-party associated with third-partydevice 750. For example, the third-party may transfer funds to thefinancial service provider to cover the deposit amount that wasdeposited into the financial service account. Settlement may occurthrough existing payment channels, such as through automated processing(e.g., through an ACH).

Through the above exemplary disclosed processes, a point of sale depositmay be completed. The point of sale deposit may have the same effect asthe point of sale deposit described above with respect to system 100,except a third-party device 750 may also be included. In theseembodiments, merchant device 120 may perform operations to complete apurchase transaction between a customer and a third-party. For example,merchant device 120 may receive transaction information (e.g., thetransaction token via the optical representation presented by clientdevice 110), receive a notification that the merchant received fundsfrom the customer, communicate with third-party device 750 to authorizethe transaction and activate the temporary account, and complete thetransaction with the customer (e.g., provide a receipt). Client device110, third-party device 750, and financial service provider device 130may communicate with each other and perform operations such that thepurchase transaction becomes a deposit transaction. In this way, thealternative embodiments of system 700 may allow for point of saledeposits while minimizing the effect on existing merchant devices.

Computer programs based on the written description and methods of thisspecification are within the skill of a software developer. The variousprograms or program modules can be created using a variety ofprogramming techniques. For example, program sections or program modulescan be designed in or by means of Java, C, C++, assembly language, orany such programming languages. One or more of such software sections ormodules can be integrated into a computer system, computer-readablemedia, or existing communications software.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as example only, with a true scope and spirit being indicatedby the following claims and their full scope of equivalents.

What is claimed is:
 1. A method for executing a point-of-sale deposit,the method comprising: receiving transaction information related to apoint-of-sale deposit; transmitting the transaction information to athird-party device; receiving a first transaction token generated by thethird-party device, wherein the first transaction token is associatedwith the transaction information and is generated based on an indicationthat a customer has transferred funds to a merchant; transmitting thefirst transaction token to a financial service provider device;transmitting a second transaction token to a merchant device; andcompleting the point-of-sale deposit based on a determination the firsttransaction token matches the second transaction token.
 2. The method ofclaim 1, wherein the transaction information is received via atransaction card action comprising at least one of a card swipe, a cardinsertion, or a near-field communication.
 3. The method of claim 1,wherein the transaction information is received via a mobileapplication.
 4. The method of claim 1, further comprising transmittingthe transaction token to the financial service provider devicewirelessly over a network.
 5. The method of claim 1, wherein thetransaction information comprises an account identifier identifying afinancial service account and an amount to be deposited into thefinancial service account, the amount to be deposited being based on anamount of funds that a merchant receives for the point-of-sale deposit.6. The method of claim 1, further comprising receiving a completionnotification from the financial service provider device indicating thatthe point-of-sale deposit was completed.
 7. The method of claim 1,wherein the third-party device is associated with a gift card provider.8. The method of claim 1, wherein the first transaction token isidentical to the second transaction token.
 9. The method of claim 1,wherein the first transaction token is different from the secondtransaction token.
 10. The method of claim 1, wherein the point-of-saledevice comprises an ATM.
 11. The method of claim 1, wherein the firsttransaction token and second token each comprise encoded transactioninformation.
 12. The method of claim 1, wherein the first transactiontoken and the second transaction token each comprise alphanumericcharacters.
 13. The method of claim 1, wherein receiving the firsttransaction token comprises receiving the first transaction token fromthe third-party device via an application programmable interface. 14.The method of claim 1, wherein: receiving the transaction informationcomprises receiving the transaction information from the merchant devicewhile a purchase transaction comprising at least one of a good orservice is taking place; the merchant device is associated with apoint-of-sale device; and the point-of-sale device being used toinitiate the point-of-sale deposit.
 15. The method of claim 1, whereinthe second transaction token is an optical representation of the firsttransaction token.
 16. The method of claim 15, further comprisingdisplaying the second transaction token.
 17. The method of claim 15,wherein the optical representation comprises at least one of a barcodereadable by a merchant device or a Quick Response (QR) code readable bya merchant device.
 18. The method of claim 1, wherein the transactioninformation comprises at least one of an amount to be deposited, anaccount identifier, an amount to purchase one or more items, or acustomer identifier.
 19. The method of claim 18, wherein the accountidentifier comprises an identifier of a financial service account toreceive the amount to be deposited.
 20. A non-transitorycomputer-readable medium storing instructions that, when executed by oneor more hardware processors, configures the one or more hardwareprocessors to perform operations for executing a point-of-sale deposit,the operations comprising: receiving transaction information related toa point-of-sale deposit; transmitting the transaction information to athird-party device; receiving a first transaction token generated by thethird-party device, wherein: the first transaction token is associatedwith the transaction information and is generated based on an indicationthat a customer has transferred funds to a merchant; transmitting thefirst transaction token to a financial service provider device;transmitting a second transaction token to a merchant device; andcompleting the point-of-sale deposit based on a determination the firsttransaction token matches the second transaction token.